feat: allow customizing tools for select backends, add thanos support #58
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is a feature I've talked about with several people already, and now
that the groundwork is laid for customizing toolsets loaded to the
server, this adds a further abstraction to allow customizing the tools
loaded by the MCP server for a specific prometheus compatible backend.
This is done by maintaining a mapping of tool name -> {description +
tool implementation}, so it's possible to maintain a mapping of
available tools and their implementations per-backend that we choose to
support.
This commit also adds initial customized support for thanos. Other
backends and tool customizations can be added in future work.
Signed-off-by: TJ Hoplock <[email protected]>
Owner
Author
oberkem
reviewed
Oct 31, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a feature I've talked about with several people already, and now
that the groundwork is laid for customizing toolsets loaded to the
server, this adds a further abstraction to allow customizing the tools
loaded by the MCP server for a specific prometheus compatible backend.
This is done by maintaining a mapping of tool name -> {description +
tool implementation}, so it's possible to maintain a mapping of
available tools and their implementations per-backend that we choose to
support.
This commit also adds initial customized support for thanos. Other
backends and tool customizations can be added in future work.
Signed-off-by: TJ Hoplock [email protected]